System for value loading onto in-vehicle device

ABSTRACT

Various embodiments are directed to using a near-filed communication (NFC) contactless card to perform one or more transactions within a vehicle. For example, a user may load value (money, funds, digital currency, etc.) onto an in-vehicle device (transponder, badge, card, etc.) by performing one-tap authentication or one-tap payment, or both, via the contactless card. Thus, even under time-constrained circumstances, payment may be loaded to the in-vehicle device in a quick, efficient, and safe manner.

BACKGROUND

Today, more and more transactions are carried out within vehicles. Forexample, a toll transponder arranged within a vehicle may be used to paytolls as the vehicle passes through toll booths or passes by transponderreaders. In another example, a garage transponder or badge may be usedto enter and park a vehicle in a parking garage. Other types ofin-vehicle transactions may involve payment for drive-through services,event access parking passes, and the like.

Typically, customers load value onto payment devices, such as theabove-described toll and garage transponders, badges, etc., by logginginto an online account and entering payment information. Often times,however, customers need to load payment onto the devices intime-constrained circumstances, e.g., immediately prior to approaching atoll booth.

Accordingly, there is a need for a quick and efficient way to load valueonto an in-vehicle device.

SUMMARY

Various embodiments are directed to using a near-filed communication(NFC) contactless card to perform one or more transactions within avehicle. For example, a user may load value (money, funds, digitalcurrency, etc.) onto an in-vehicle device (transponder, badge, card,etc.) by performing one-tap authentication or one-tap payment, or both,via the contactless card. Thus, even under time-constrainedcircumstances, payment may be loaded to the in-vehicle device in aquick, efficient, and safe manner.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example data transmission system in accordancewith one or more embodiments.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access in accordance with one or more embodiments.

FIG. 2 illustrates an example system using a contactless card inaccordance with one or more embodiments.

FIG. 3A illustrates an example contactless card in accordance with oneor more embodiments.

FIG. 3B illustrates an example contact pad of a contactless card inaccordance with one or more embodiments.

FIG. 4 illustrates an example sequence diagram relating to securepassword generation in accordance with one or more embodiments.

FIG. 5 illustrates an example password generation for a password managerapplication in accordance with one or more embodiments.

FIG. 6 illustrates another example of a sequence diagram relating tosecure password generation in accordance with one or more embodiments.

FIG. 7 illustrates another example of password generation for a websitein accordance with one or more embodiments.

DETAILED DESCRIPTION

Various embodiments are generally directed to a system for loading value(e.g., money) onto an in-vehicle device using at least a contactlessnear-field communication (NFC) smartcard. In examples, the in-vehicledevice may be any suitable device arranged or located within a vehicleand may be used to perform various transactions. In some examples, thein-vehicle device may be built into the vehicle.

According to one embodiment, the in-vehicle device may be a tolltransponder. When a user wishes to reload or add funds onto an existingweb-based account corresponding to the toll transponder, the user maytap a mobile computing device, such as a smartphone, to the tolltransponder, which may read one or more types of account-relatedinformation so that the mobile computing device can access the account.Thus, when the smartphone, for instance, is tapped, the smartphone mayread a uniform resource locator (URL) from the toll transponder, whichallows the smartphone to launch a toll-specific payment application or awebsite. The user may then tap a contactless smartcard to the smartphoneto reload the account. In examples, the reload amount may be apredetermined value set by the user, e.g., $20. It may be understoodthat a toll transponder may be just an example of the in-vehicle deviceand not limited thereto. The in-vehicle device may any type oftransponder that allows payments to be deducted from an associatedaccount.

According to another embodiment, a contactless card may be directlytapped to an in-vehicle device without the use of a mobile computingdevice. For example, value (e.g., funds) may be loaded onto thein-vehicle transponder directly via “contactless” authentication andpayment (e.g., using the contactless smartcard) without the use of anexternal web-based account.

According to a further embodiment, an in-vehicle device may beintegrated into a vehicle and coupled to the various electroniccomponents of the vehicle. For example, the vehicle may have aninterface point for reading a contactless smartcard for value loading.The interface point may be located on a dashboard or the center consoleof the vehicle. In another example, a secure interface may be arrangedin the vehicle such that the contactless smartcard can be secured intoplace when the user is in the vehicle, and further, can be removed whenthe user leaves the vehicle. In further examples, the in-vehicle deviceintegrated in the vehicle may be used as authentication mechanism toauthenticate the vehicle, e.g., when entering and parking in a parkinggarage.

In previous solutions, the value loading process has been a tedioustask. As described above, a user typically had to login to the user'sonline account and enter payment information, all of which was requiredto be performed prior to driving a vehicle. And generally, previoussolutions have been unable to effectively coordinate and facilitatetransactions within a vehicle. The embodiments and examples describedherein overcome and are advantageous over the previous solutions in thatan NFC enabled contactless smart card may be used to quickly load valueonto in-vehicle devices, even under time-constrained circumstances(e.g., as the vehicle approaches a toll booth or a transponder reader).Also, because the contactless card itself is uniquely associated withthe user, the card can be used to quickly authenticate the user withinthe vehicle, e.g., parking.

Reference is now made to the drawings, where like reference numerals areused to refer to like elements throughout. In the following description,for the purpose of explanation, numerous specific details are set forthin order to provide a thorough understanding thereof. It may be evident,however, that the novel embodiments can be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form to facilitate a description thereof. Theintention is to cover all modification, equivalents, and alternativeswithin the scope of the claims.

FIG. 1A illustrates an example data transmission system according to oneor more embodiments. As further discussed below, system 100 may includecontactless card 105, client device 110, network 115, and server 120.Although FIG. 1A illustrates single instances of the components; system100 may include any number of components.

System 100 may include one or more contactless cards 105, which arefurther explained below with reference to FIG. 3A and FIG. 3B. In someembodiments, contactless card 105 may be in wireless communication,utilizing NFC in an example, with client device 110.

System 100 may include client device 110, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a phone, a smartphone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. Client device 110 also may be a mobile computing device, forexample, an iPhone, iPod, iPad from Apple® or any other suitable devicerunning Apple's iOS® operating system, any device running Microsoft'sWindows® Mobile operating system, any device running Google's Android®operating system, and/or any other suitable mobile computing device,such as a smartphone, a tablet, or like wearable mobile device.

The client device 110 device can include a processor and a memory, andit is understood that the processing circuitry may contain additionalcomponents, including processors, memories, error and parity/CRCcheckers, data encoders, anti-collision algorithms, controllers, commanddecoders, security primitives, and tamper-proofing hardware, asnecessary to perform the functions described herein. The client device110 may further include a display and input devices. The display may beany type of device for presenting visual information such as a computermonitor, a flat panel display, and a mobile device screen, includingliquid crystal displays, light-emitting diode displays, plasma panels,and cathode ray tube displays. The input devices may include any devicefor entering information into the user's device that is available andsupported by the user's device, such as a touch-screen, keyboard, mouse,cursor-control device, touch-screen, microphone, digital camera, videorecorder or camcorder. These devices may be used to enter informationand interact with the software and other devices described herein.

In some examples, client device 110 of system 100 may execute one ormore applications, such as software applications, that enable, forexample, network communications with one or more components of system100 and transmit and/or receive data.

Client device 110 may be in communication with one or more servers 120via one or more networks 115 and may operate as a respective front-endto back-end pair with server 120. Client device 110 may transmit, forexample from a mobile device application executing on client device 110,one or more requests to server 120. The one or more requests may beassociated with retrieving data from server 120. Server 120 may receivethe one or more requests from client device 110. Based on the one ormore requests from client device 110, server 120 may be configured toretrieve the requested data from one or more databases (not shown).Based on receipt of the requested data from the one or more databases,server 120 may be configured to transmit the received data to clientdevice 110, the received data being responsive to one or more requests.

System 100 may include one or more networks 115. In some examples,network 115 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network and may beconfigured to connect client device 110 to server 120. For example,network 115 may include one or more of a fiber optics network, a passiveoptical network, a cable network, an Internet network, a satellitenetwork, a wireless local area network (LAN), a Global System for MobileCommunication, a Personal Communication Service, a Personal AreaNetwork, Wireless Application Protocol, Multimedia Messaging Service,Enhanced Messaging Service, Short Message Service, Time DivisionMultiplexing based systems, Code Division Multiple Access (CDMA) basedsystems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1,802.11n and 802.11g, Bluetooth, NFC, Radio Frequency Identification(RFID), Wi-Fi, and/or the like.

In addition, network 115 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a LAN, or a global network such as theInternet. In addition, network 115 may support an Internet network, awireless communication network, a cellular network, or the like, or anycombination thereof. Network 115 may further include one network, or anynumber of the exemplary types of networks mentioned above, operating asa stand-alone network or in cooperation with each other. Network 115 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 115 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 115 is depicted as a single network, it should be appreciatedthat according to one or more examples, network 115 may include aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, such as credit card association networks, and homenetworks.

System 100 may include one or more servers 120. In some examples, server120 may include one or more processors, which are coupled to the memory.Server 120 may be configured as a central system, server or platform tocontrol and call various data at different times to execute a pluralityof workflow actions. Server 120 may be configured to connect to the oneor more databases. Server 120 may be connected to at least one clientdevice 110.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access according to one or more embodiments. The diagrammay include contactless card 105 and client device 110, which mayinclude an application 122 and processor 124. FIG. 1B may referencesimilar components as illustrated in FIG. 1A.

At step 102, the application 122 communicates with the contactless card105 (e.g., after being brought near the contactless card 105).Communication between the application 122 and the contactless card 105may involve the contactless card 105 being sufficiently close to a cardreader (not shown) of the client device 110 to enable NFC data transferbetween the application 122 and the contactless card 105.

At step 104, after communication has been established between clientdevice 110 and contactless card 105, the contactless card 105 generatesa message authentication code (MAC) cryptogram. In some examples, thismay occur when the contactless card 105 is read by the application 122.In particular, this may occur upon a read, such as an NFC read, of anear field data exchange (NDEF) tag, which may be created in accordancewith the NFC Data Exchange Format.

For example, a reader, such as application 122, may transmit a message,such as an applet select message, with the applet ID of an NDEFproducing applet. Upon confirmation of the selection, a sequence ofselect file messages followed by read file messages may be transmitted.For example, the sequence may include “Select Capabilities file,” “ReadCapabilities file,” and “Select NDEF file.” At this point, a countervalue maintained by the contactless card 105 may be updated orincremented, which may be followed by “Read NDEF file.” At this point,the message may be generated which may include a header and a sharedsecret. Session keys may then be generated. The MAC cryptogram may becreated from the message, which may include the header and the sharedsecret. The MAC cryptogram may then be concatenated with one or moreblocks of random data, and the MAC cryptogram and a random number (RND)may be encrypted with the session key. Thereafter, the cryptogram andthe header may be concatenated, and encoded as ASCII hex and returned inNDEF message format (responsive to the “Read NDEF file” message).

In some examples, the MAC cryptogram may be transmitted as an NDEF tag,and in other examples, the MAC cryptogram may be included with a uniformresource indicator (e.g., as a formatted string).

In some examples, application 122 may be configured to transmit arequest to contactless card 105, the request comprising an instructionto generate a MAC cryptogram.

At step 106, the contactless card 105 sends the MAC cryptogram to theapplication 122. In some examples, the transmission of the MACcryptogram occurs via NFC. However, the present disclosure is notlimited thereto. In other examples, this communication may occur viaBluetooth, Wi-Fi, or other means of wireless data communication.

At step 108, the application 122 communicates the MAC cryptogram to theprocessor 124. At step 112, the processor 124 verifies the MACcryptogram pursuant to an instruction from the application 122. Forexample, the MAC cryptogram may be verified, as explained below.

In some examples, verifying the MAC cryptogram may be performed by adevice other than client device 110, such as a server 120 in datacommunication with the client device 110 (as shown in FIG. IA). Forexample, processor 124 may output the MAC cryptogram for transmission toserver 120, which may verify the MAC cryptogram.

In some examples, the MAC cryptogram may function as a digital signaturefor purposes of verification. Other digital signature algorithms, suchas public key asymmetric algorithms, e.g., the Digital SignatureAlgorithm and the RSA algorithm, or zero knowledge protocols, may beused to perform this verification.

It may be understood that in some examples, the contactless card 105 mayinitiate communication after the contactless card is brought near theclient device 110. By way of example, the contactless card 105 may sendthe client device 110 a message, for instance, indicating that thecontactless card has established communication. Thereafter, theapplication 122 of client device 110 may proceed to communicate with thecontactless card at step 102, as described above.

FIG. 2 illustrates an example system 200 using a contactless card.System 200 may include a contactless card 205, one or more clientdevices 210, network 215, servers 220, 225, one or more hardwaresecurity modules 230, and a database 235. Although FIG. 2 illustratessingle instances of the components, system 200 may include any number ofcomponents.

System 200 may include one or more contactless cards 205, which arefurther explained below with respect to FIG. 3A and FIG. 3B. In someexamples, contactless card 205 may be in wireless communication, forexample, NFC communication, with client device 210. For example,contactless card 205 may include one or more chips, such as a radiofrequency identification chip, configured to communicate via NFC orother short-range protocols. In other embodiments, contactless card 205may communicate with client device 210 through other means including,but not limited to, Bluetooth, satellite, Wi-Fi, wired communications,and/or any combination of wireless and wired connections. According tosome embodiments, contactless card 205 may be configured to communicatewith card reader 213 (which may otherwise be referred to herein as NFCreader, NFC card reader, or reader) of client device 210 through NFCwhen the contactless card 205 is within range of card reader 213. Inother examples, communications with contactless card 205 may beaccomplished through a physical interface, e.g., a universal serial businterface or a card swipe interface.

System 200 may include client device 210, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to: e.g., a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a mobile device, a phone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. One or more client devices 210 also may be a mobile device; forexample, a mobile device may include an iPhone, iPod, iPad from Apple®or any other mobile device running Apple's iOS® operating system, anydevice running Microsoft's Windows® Mobile operating system, any devicerunning Google's Android® operating system, and/or any other smartphoneor like wearable mobile device. In some examples, the client device 210may be the same as, or similar to, a client device 110 as described withreference to FIG. 1A or FIG. 1B.

Client device 210 may be in communication with one or more servers 220and 225 via one or more networks 215. Client device 210 may transmit,for example from an application 211 executing on client device 210, oneor more requests to one or more servers 220 and 225. The one or morerequests may be associated with retrieving data from one or more servers220 and 225. Servers 220 and 225 may receive the one or more requestsfrom client device 210. Based on the one or more requests from clientdevice 210, one or more servers 220 and 225 may be configured toretrieve the requested data from one or more databases 235. Based onreceipt of the requested data from the one or more databases 235, one ormore servers 220 and 225 may be configured to transmit the received datato client device 210, the received data being responsive to one or morerequests.

System 200 may include one or more hardware security modules (HSM) 230.For example, one or more HSMs 230 may be configured to perform one ormore cryptographic operations as disclosed herein. In some examples, oneor more HSMs 230 may be configured as special purpose security devicesthat are configured to perform the one or more cryptographic operations.The HSMs 230 may be configured such that keys are never revealed outsidethe HSM 230, and instead, are maintained within the HSM 230. Forexample, one or more HSMs 230 may be configured to perform at least oneof key derivations, decryption, and MAC operations. The one or more HSMs230 may be contained within or may be in data communication with,servers 220 and 225.

System 200 may include one or more networks 215. In some examples,network 215 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network, and may beconfigured to connect client device 210 to servers 220 and/or 225. Forexample, network 215 may include one or more of a fiber optics network,a passive optical network, a cable network, a cellular network, anInternet network, a satellite network, a wireless LAN, a Global Systemfor Mobile Communication, a Personal Communication Service, a PersonalArea Network, Wireless Application Protocol, Multimedia MessagingService, Enhanced Messaging Service, Short Message Service, TimeDivision Multiplexing based systems, Code Division Multiple Access based(CDMA) systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n and 802.11g, Bluetooth, NFC, RFID, Wi-Fi, and/or anycombination of networks thereof. As a non-limiting example,communications from contactless card 205 and client device 210 mayinclude NFC communication, the cellular network between client device210 and a carrier, and Internet between the carrier and a back-end.

In addition, network 215 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a local area network, or a globalnetwork such as the Internet. In addition, network 215 may support anInternet network, a wireless communication network, a cellular network,or the like, or any combination thereof. Network 215 may further includeone network, or any number of the exemplary types of networks mentionedabove, operating as a stand-alone network or in cooperation with eachother. Network 215 may utilize one or more protocols of one or morenetwork elements to which they are communicatively coupled. Network 215may translate to or from other protocols to one or more protocols ofnetwork devices. Although network 215 is depicted as a single network,it should be appreciated that according to one or more examples, network215 may include a plurality of interconnected networks, such as, forexample, the Internet, a service provider's network, a cable televisionnetwork, corporate networks, such as credit card association networks,and home networks.

In various examples according to the present disclosure, client device210 of system 200 may execute one or more applications 211 and includeone or more processors 212, and one or more card readers 213. Forexample, one or more applications 211, such as software applications,may be configured to enable, for example, network communications withone or more components of system 200 and transmit and/or receive data.It is understood that although only single instances of the componentsof client device 210 are illustrated in FIG. 2, any number of devices210 may be used. Card reader 213 may be configured to read from and/orcommunicate with contactless card 205. In conjunction with the one ormore applications 211, card reader 213 may communicate with thecontactless card 205. In examples, the card reader 213 may includecircuitry or circuitry components, e.g., NFC reader coil, that generatesa magnetic field to allow communication between the client device 210and the contactless card 205.

The application 211 of any of client device 210 may communicate with thecontactless card 205 using short-range wireless communication (e.g.,NFC). The application 211 may be configured to interface with a cardreader 213 of client device 210 configured to communicate with acontactless card 205. As should be noted, those skilled in the art wouldunderstand that a distance of less than twenty centimeters is consistentwith NFC range.

In some embodiments, the application 211 communicates through anassociated reader (e.g., card reader 213) with the contactless card 205.

In some embodiments, card activation may occur without userauthentication. For example, a contactless card 205 may communicate withthe application 211 through the card reader 213 of the client device 210through NFC. The communication (e.g., a tap of the card proximate thecard reader 213 of the client device 210) allows the application 211 toread the data associated with the card and perform an activation. Insome cases, the tap may activate or launch application 211 and theninitiate one or more actions or communications with an account server225 to activate the card for subsequent use. In some cases, if theapplication 211 is not installed on client device 210, a tap of the cardagainst the card reader 213 may initiate a download of the application211 (e.g., navigation to an application download page). Subsequent toinstallation, a tap of the card may activate or launch the application211, and then initiate (e.g., via the application or other back-endcommunication) activation of the card. After activation, the card may beused in various transactions including commercial transactions.

According to some embodiments, the contactless card 205 may include avirtual payment card. In those embodiments, the application 211 mayretrieve information associated with the contactless card 205 byaccessing a digital wallet implemented on the client device 210, whereinthe digital wallet includes the virtual payment card. In some examples,virtual payment card data may include one or more static or dynamicallygenerated virtual card numbers.

Server 220 may include a web server in communication with database 235.Server 225 may include an account server. In some examples, server 220may be configured to validate one or more credentials from contactlesscard 205 and/or client device 210 by comparison with one or morecredentials in database 235. Server 225 may be configured to authorizeone or more requests, such as payment and transaction, from contactlesscard 205 and/or client device 210.

FIG. 3A illustrates one or more contactless cards 300, which may includea payment card, such as a credit card, debit card, or gift card, issuedby a service provider 305 displayed on the front or back of the card300. In some examples, the contactless card 300 is not related to apayment card and may include, without limitation, an identificationcard. In some examples, the payment card may include a dual interfacecontactless payment card. The contactless card 300 may include asubstrate 310, which may include a single layer or one or more laminatedlayers composed of plastics, metals, and other materials. Exemplarysubstrate materials include polyvinyl chloride, polyvinyl chlorideacetate, acrylonitrile butadiene styrene, polycarbonate, polyesters,anodized titanium, palladium, gold, carbon, paper, and biodegradablematerials. In some examples, the contactless card 300 may have physicalcharacteristics compliant with the ID-1 format of the ISO/IEC 7810standard, and the contactless card may otherwise be compliant with theISO/IEC 14443 standard. However, it is understood that the contactlesscard 300 according to the present disclosure may have differentcharacteristics, and the present disclosure does not require acontactless card to be implemented in a payment card.

The contactless card 300 may also include identification information 315displayed on the front and/or back of the card, and a contact pad 320.The contact pad 320 may be configured to establish contact with anothercommunication device, such as a user device, smart phone, laptop,desktop, or tablet computer. The contactless card 300 may also includeprocessing circuitry, antenna and other components not shown in FIG. 3A.These components may be located behind the contact pad 320 or elsewhereon the substrate 310. The contactless card 300 may also include amagnetic strip or tape, which may be located on the back of the card(not shown in FIG. 3A).

As illustrated in FIG. 3B, the contact pad 320 of FIG. 3A may includeprocessing circuitry 325 for storing and processing information,including a microprocessor 330 and a memory 335. It is understood thatthe processing circuitry 325 may contain additional components,including processors, memories, error and parity/CRC checkers, dataencoders, anti-collision algorithms, controllers, command decoders,security primitives and tamper-proofing hardware, as necessary toperform the functions described herein.

The memory 335 may be a read-only memory, write-once read-multiplememory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card 300 may include one or more of these memories. Aread-only memory may be factory programmable as read-only or one-timeprogrammable. One-time programmability provides the opportunity to writeonce then read many times. A write once/read-multiple memory may beprogrammed at a point in time after the memory chip has left thefactory. Once the memory is programmed, it may not be rewritten, but itmay be read many times. A read/write memory may be programmed andre-programmed many times after leaving the factory. It may also be readmany times.

The memory 335 may be configured to store one or more applets 340, oneor more counters 345, and a customer identifier 350. The one or moreapplets 340 may include one or more software applications configured toexecute on one or more contactless cards, such as Java Card applet.However, it is understood that applets 340 are not limited to Java Cardapplets, and instead may be any software application operable oncontactless cards or other devices having limited memory. The one ormore counters 345 may include a numeric counter sufficient to store aninteger. The customer identifier 350 may include a unique alphanumericidentifier assigned to a user of the contactless card 300, and theidentifier may distinguish the user of the contactless card from othercontactless card users. In some examples, the customer identifier 350may identify both a customer and an account assigned to that customerand may further identify the contactless card associated with thecustomer's account.

The processor and memory elements of the foregoing exemplary embodimentsare described with reference to the contact pad, but the presentdisclosure is not limited thereto. It is understood that these elementsmay be implemented outside of the pad 320 or entirely separate from itor as further elements in addition to processor 330 and memory 335elements located within the contact pad 320.

In some examples, the contactless card 300 may include one or moreantennas 355. The one or more antennas 355 may be placed within thecontactless card 300 and around the processing circuitry 325 of thecontact pad 320. For example, the one or more antennas 355 may beintegral with the processing circuitry 325 and the one or more antennas355 may be used with an external booster coil. As another example, theone or more antennas 355 may be external to the contact pad 320 and theprocessing circuitry 325.

In an embodiment, the coil of contactless card 300 may act as thesecondary of an air core transformer. The terminal may communicate withthe contactless card 300 by cutting power or amplitude modulation. Thecontactless card 300 may infer the data transmitted from the terminalusing the gaps in the contactless card's power connection, which may befunctionally maintained through one or more capacitors. The contactlesscard 300 may communicate back by switching a load on the contactlesscard's coil or load modulation. Load modulation may be detected in theterminal's coil through interference.

As explained above, the contactless cards 300 may be built on a softwareplatform operable on smart cards or other devices having limited memory,such as JavaCard, and one or more or more applications or applets may besecurely executed. Applets may be added to contactless cards to providea one-time password (OTP) for multifactor authentication (MFA) invarious mobile application-based use cases. Applets may be configured torespond to one or more requests, such as near field data exchangerequests, from a reader, such as a mobile NFC reader, and produce anNDEF message that includes a cryptographically secure OTP encoded as anNDEF text tag.

FIG. 4 illustrates an example sequence diagram 400 for loading valueonto an in-vehicle device 404 using a mobile computing device 402 and acontactless card 406 according to one or more embodiments. The mobilecomputing device 402 may be a client device, such as a smartphone, alaptop, a tablet computer, a wearable computer, etc., configured totransmit and received information with in-vehicle device 404 and thecontactless card 406. As described above, the mobile computing device402 may include at least an NFC card reader configured to establish NFCcommunication with the contactless card 406.

At step 412, the mobile computing device 402 may receive or obtain aunique identifier (ID) associated with the in-vehicle device 404. Inexamples, the in-vehicle device 404 may be a toll transponder, a devicefor drive-thru payment service, a garage access transponder or badge, aparking pass, etc. The unique ID associated with the in-vehicle device404 may be derived from one or more barcodes displayed thereon or anyother suitable identifier, such as an in-vehicle device number, name,transponder identification number, an account number associated with thedrive-thru payment service, a badge number associated with the garageaccess transponder or badge, pass number corresponding to the parkingpass, etc. In other examples, the in-vehicle device 404 may include oneor more NFC tags or radio frequency identification (RFID) tags that cantransmit the unique ID information. Moreover, the computing device 402may receive or obtain information for accessing an account (online orotherwise) associated with the in-vehicle device 404. For example, theinformation may include at least a uniform resource locator (URL) foraccessing an online account.

Upon receiving the unique ID of the in-vehicle device 404 and theinformation for accessing an account associated with the device, at step414, the mobile computing device 402 may access the account associatedwith the device to at least load funds into the account.

At step 416, communication may be established between the mobilecomputing device 402 and the contactless card 406. In examples, thecommunication may be automatically established upon the contactless cardentering the magnetic field generated by an NFC reader of the mobilecomputing device 402. In other examples, the mobile computing device 402may first establish communication by sending the contactless card 406 asignal when the computing device 402 detects that the contactless card406 has entered the magnetic field of the NFC reader. As will bedescribed below, a user may use the contactless card 406 to performone-tap authentication and one-tap payment on the mobile computingdevice 402, which advantageously makes the value loading process quickand simple for the user while in the vehicle.

At step 418, value (e.g., funds, digital currency, entity or businessspecific value, etc.) may be loaded into the account via the tapping ofthe contactless card 406 to the mobile computing device 402. Uponloading the account, at step 420, the account associated the in-vehicledevice 404 may be updated to reflect the added value. Thereafter, atstep 422, the in-vehicle device 404 may communicate with one or morereaders to process or deduct payment(s) from the account.

It may be understood that the steps shown in the sequence diagram 400are for illustrative purposes and not intended to be limiting in anymanner. Thus, the steps are not required to be performed in any specificorder.

FIG. 5 illustrates an example value loading process using one-tapauthentication and one-tap payment according to one or more embodiments.In FIG. 5, a view 500 is shown, which visually represents what a user(e.g., driver, passenger, etc.) would see within a vehicle as the userapproaches a toll booth 504 and transponder reader 506. In examples, asthe user is approaching the toll area, the user may realize that thereare insufficient funds in the user's online toll-pay account to pay thetoll.

To initiate the one-tap value loading process, as shown, the user maytap smartphone 506 to a toll transponder 508. Alternatively, thesmartphone 506 may capture one or more images of the toll transponder.In either or both instances, the smartphone may receive at least twopieces of information, as described above. First, the smartphone 506 mayreceive a unique identifier associated with the transponder, which maybe a transponder number, a barcode number, or any other type ofinformation that specifically identifies the transponder 508 so that,for example, the correct transponder is identified and loaded. Second,the smartphone 506 may receive information on where and how to accessthe user's online toll-pay account. In examples, the information may bein the form of a URL that links to the online account, mobileapplication, etc. The information may be physically displayed or locatedon the transponder 508 itself. It may be understood that the transponderID and account-related information may be stored on the smartphone 506for future use. Moreover, it may be understood that the aforementionedtransponder ID and information may be received, accessed, or retrievedwirelessly from the transponder 508 via NFC and/or RFID communication.

Upon accessing the toll-pay account corresponding to the user, acontactless card 510 may be used to perform one-tap user authenticationand one-tap value loading (e.g., loading or reloading the account,one-time payment, etc.). It may be understood that the contactless card510 may be similar or identical to the contactless card 300 describedabove. Moreover, it may be understood that the funds or money loadedinto the toll-pay account may be linked to one or more banking accountscorresponding to the contactless card 510.

As illustrated, a toll-pay account website, mobile application, or anyother suitable payment application or website may be displayed on agraphical user interface (GUI) module 512 to perform one-tapauthentication and one-tap payment. In examples, a notification (notshown) may instruct the user to tap the contactless card 510 to thesmartphone 506 to authenticate into the user's toll-pay account. Uponthe user tapping the contactless card 510 to the smartphone 506, thecontactless card 510 may generate encrypted data and transmit the sameto the smartphone 506. Once received, the one-tap GUI module 512 maytransmit at least the encrypted data to one or more authenticationservers, which may decrypt the data and verify the data with a privatekey stored in the memory of the server. The authentication server maythen authenticate the user of the contactless card 510 and send thesmartphone 506 confirmation thereof.

Moreover, confirmation of the authentication of the user via the one-tapauthentication may also be used to authenticate and automatically logthe user into the user's toll-pay account, for example, withoutrequiring the user to enter login information and a password. Inexamples, the authentication server may communicate with one or moretoll-pay account servers to verify or confirm such authentication, or inother examples, the user may identify or register with the toll-payaccount beforehand the contactless card 510 as an authentication tool.

As shown, after the user has been authenticated and logged into thetoll-pay account, the GUI module 512 may display various information,such as a current balance on the account and a preset load value, whichmay be $50 as indicated in FIG. 5. Moreover, the GUI module 512 maydisplay a notification 514 that directs the user to tap the contactlesscard 510 for payment to or loading or reloading of the account. It maybe understood that, in some examples, both the authentication and valueloading processes may be performed automatically based on a single tapof the contactless card 510, as opposed to a separate tap forauthentication and another tap for payment. Furthermore, the one-tapauthentication and payment features may be audibly presented to the userso that the user does not have to look at the smartphone 506 orotherwise be distracted if driving.

When the contactless card 506 is tapped to the smartphone 506, amerchant ID and a transaction ID may be sent to the above-described oneor more authentication servers. A virtual account number (VAN) generatormay be used to generate virtual card data (e.g., a virtual card number,expiration date, and/or CVV) associated with the contactless card 510.The VAN generator may then transmit the virtual card data, the merchantID, transaction ID, and any usernames and/or addresses corresponding tothe user to one or more merchant servers (e.g., toll-pay merchant orprovider). The merchant server may then process the transaction usingthe data received from the VAN generator, e.g., by generating atransaction record in a transaction database using at least the receivedvirtual card number, expiration date, CVV, etc. The transaction recordmay further include the user's name, billing address, shipping address,and an indication of each item and/or service purchased. The merchantserver may then transmit an order (e.g., value reload) confirmation tothe mobile computing device 404.

The one-tap authentication and payment via the smartphone 506, thetransponder 508, and the contactless card 510 may be used, performed,operated, completed, etc. in the vehicle and prior to the user passingthrough the toll booth 504 and/or the transponder reader 516, at whichpoint the requisite fee may be deducted from the user's online account.Accordingly, the use of the contactless card 510 and user's mobilecomputing device advantageously allows the value loading process to bequick, easy, and safe.

FIG. 6 illustrates an example value loading process directly between acontactless card 601 and an in-vehicle device 602 according to one ormore embodiments. As described above, the in-vehicle device 602 may be atoll transponder, a garage access transponder or badge, a device for adrive-thru payment service, a parking pass, etc. As shown, thein-vehicle device 602 may include various components, such as one ormore processors 604, memory 606, NFC reader 608, an insert interface 610(which may be optional in some examples), a power interface 612, and anamplifier 614. It may be understood that the contactless card 601 may besimilar or identical to the contactless card 300 described above.

In examples, a user may tap the contactless card 601 directly to thein-vehicle device 602 without the use of a mobile computing device. Inalternative example, the contactless card 601 may be inserted into theinsert interface 610, which may be a card slot to accommodate thecontactless card 601. A banking account associated with the contactlesscard 601 may be linked to an account associated with the in-vehicledevice 602 (e.g., upon contact or beforehand), or in other examples, thefunds in the banking account may be accessed by the in-vehicle device602 in real-time or near real-time for loading the account associatedwith the in-vehicle device 602.

According to embodiments, the in-vehicle device 602 may determinewhether the contactless card 601 has established communication with thein-vehicle device via the NFC reader or the insert interface. The valueloading process may initiate upon a determination of establishedcommunication. Moreover, the in-vehicle device 602 may determine whethercommunication has been established with an external in-vehicle devicereader (not shown). It may be understood that when the user taps thecontactless card 601, or inserts it into the insert interface 610, toinitiate the value loading process, the in-vehicle device 602 may “lookfor” the communication with the external reader for a predeterminedperiod of time (e.g., 10 minutes, 5 minutes, 1 minute, 30 seconds, etc.)in the event, for example, it takes the user some time to pass throughor by the external reader.

When communication between the in-vehicle device 602 and the externalreader has been established, one or more payment values may be loaded tothe account associated with the in-vehicle device 602 from the linkeduser banking account so that loaded values can be deducted by theexternal reader. For example, the communicative presence of the externalreader may trigger the in-vehicle device 602 to transmit data to theexternal reader indicating at least “the user has specified andallocated the requisite payment value from an authorized bankingaccount, so load that payment value to the in-vehicle device account anddeduct the payment.” Thus, for instance, if a toll fee is five dollars,the transmitted data to a toll transponder reader may be “the userauthorized the five-dollar toll payment from the user's contactlesscard, so load that amount and deduct.” In at least that regard, theaccount associated with the in-vehicle device may not be a conventionalweb-based account, such as the one described above in FIGS. 4 and 5, butmay simply be a “pass-through” account that passes the requisite paymentvalues from the contactless card banking account to the entityrequesting payment.

In some examples, the facilitation of the value loading and deductionmay be performed by one or more server computers (which may be managedby the entity requesting and receiving payment) based at least in parton the data transmitted from the in-vehicle device 602 to the externalreader (which may be in communication with the one or more servers).

As shown, the in-vehicle device 602 may include or incorporate a powerinterface 612 for drawing power from the vehicle, which may be done viaa vehicle power socket, or in other examples, the power may be providedby one or more energy storage components, such as a battery, acapacitor, etc. Moreover, the amplifier 614 may be configured to amplifysignals from the in-vehicle device 602 to the external reader, forexample, to improve or lengthen communication capabilities between thein-vehicle device 602 and the external reader.

FIG. 7 illustrates an example authentication and/or value loadingprocess using components integrated in a vehicle 700 according to one ormore embodiments. As shown from view 702, an in-vehicle device 710 maybe integrated in the vehicle 700 on the driver-side of the centerconsole. While the device 710 is shown to have a generally oval shape,it may be understood that the reader can be rectangular, square, or anyother suitable shape, design, or configuration. An NFC reader and/orRFID reader may be incorporated in the in-vehicle device 710. Moreover,the vehicle 700 may include one or more vehicle computing devices (notshown) and other components for at least performing and facilitatingtransactions in the vehicle.

In one example, a user may tap a contactless card 720 to the in-vehicledevice 710 to perform authentication. For example, the in-vehicle device710 may be used to authenticate a user when entering a parking garage byproviding authentication information to an external reader. In otherexamples, the vehicle 700 may include a secure storage area 712 wherethe contactless card 720 can be locked into place. The storage area 712may also include an NFC reader and/or an RFID reader.

In further examples, the in-vehicle device 710, the vehicle computingdevice, and the mobile computing device 722 may all separately includeBluetooth interfaces (or any other suitable interfaces) for short-rangewireless communication. The authentication information, for instance,may be transmitted to the vehicle computing device from the in-vehicledevice 710 via the respective short-range wireless communicationinterfaces. Moreover, the mobile computing device 722 may communicatewith the vehicle computing device and/or the in-vehicle device 710. Forexample, the user may control or manage value loading onto an accountassociated with the in-vehicle device 710 using the mobile computingdevice 722, such as transferring funds from the contactless card 720 tothe in-vehicle device 710 via the Bluetooth interfaces of the vehiclecomputing device to the in-vehicle device 710. It may be understood thatthe short-range wireless communications among the interfaces of thein-vehicle device 710, the vehicle computing device, and the mobilecomputing device 722 may be authenticated and secure.

Accordingly, the user may be able to optionally tap the contactless card720 to either the in-vehicle device 710 or the mobile computing device722 to perform authentication and/or value loading. Moreover, in someexamples, the user may use the vehicle computing device to control theauthentication and value loading features (e.g., via a display device inthe vehicle) and/or the user may use the mobile computing device 722 tocontrol such features, as described above.

The components and features of the devices described above may beimplemented using any combination of discrete circuitry, applicationspecific integrated circuits (ASICs), logic gates and/or single chiparchitectures. Further, the features of the devices may be implementedusing microcontrollers, programmable logic arrays and/or microprocessorsor any combination of the foregoing where suitably appropriate. It isnoted that hardware, firmware and/or software elements may becollectively or individually referred to herein as “logic” or “circuit.”

At least one computer-readable storage medium may include instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Moreover, unless otherwise noted the features described above arerecognized to be used together in any combination. Thus, any featuresdiscussed separately may be employed in combination with each otherunless it is noted that the features are incompatible with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form part of one or more embodiments.Rather, the operations are machine operations.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose and may be selectively activated or reconfigured by acomputer program stored in the computer. The procedures presented hereinare not inherently related to a particular computer or other apparatus.The required structure for a variety of these machines will appear fromthe description given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

1. A system for value loading onto an in-vehicle device, the systemcomprising: a computing device comprising: a near-field communication(NFC) reader; a memory storing one or more instructions; and one or moreprocessors, coupled with the memory, operable to execute the one or moreinstructions, that when executed, cause the one or more processors to:receive one or more images of a unique identifier associated with thein-vehicle device in response to the camera being within a predefineddistance from the in-vehicle device; receive one or more images ofinformation for accessing an account associated with the in-vehicledevice in response to the camera being within the predefined distancefrom the in-vehicle device, the information including at least a uniformresource locator (URL) corresponding to the account; detect a first tapof a contactless card belonging to a user and, in response to the firsttap, authenticate the user, wherein the authentication comprises: (i)detecting the contactless card via the NFC reader, the contactless cardbeing tapped to the computing device by the user, (ii) receivingencrypted data from the contactless card via NFC, the encrypted dataincluding at least a customer identifier, the customer identifier beingassociated with the user (iii) performing user authentication by:sending the encrypted data including the customer identifier to one ormore remote computing devices, wherein the one or more remote computingdevices performs at least decryption of the data using a key, andreceiving an indication or confirmation from the remote computingdevices that the customer identifier matches the user, and (iv)determining that user authentication is successful based on the customeridentifier matching the user; access, automatically in response tosuccessful authentication of the user, the account associated with thein-vehicle device based on the URL and the unique identifier of thein-vehicle device without requiring the user to enter login information;and detect a second tap of the contactless card, and in response to thesecond tap, load or reload the account associated with the in-vehicledevice with funds of a predetermined value or amount, wherein the fundsare linked to a banking account corresponding to the contactless card.2. The system of claim 1, wherein the in-vehicle device is a tolltransponder, a device for drive-thru payment service, a garage accessbadge, or a parking pass.
 3. The system of claim 1, wherein thecomputing device is a smartphone, a laptop, a tablet computer, or awearable computer.
 4. The system of claim 1, wherein the computingdevice is tapped to the in-vehicle device to receive the uniqueidentifier and/or the information for accessing the account associatedwith the in-vehicle device.
 5. The system of claim 4, wherein thecontactless card is tapped to the computing device to load or reload theaccount associated with the in-vehicle device.
 6. The system of claim 2,wherein the unique identifier associated with the in-vehicle device is(i) a transponder identification number, (i) an account numbercorresponding to the drive-thru payment service, (iii) a badge numbercorresponding to the garage access badge, and/or (iv) pass numbercorresponding to the parking pass.
 7. (canceled)
 8. The system of claim1, wherein the account is provided via a payment application and/or awebsite.
 9. The system of claim 1, wherein the one or more processors ofthe computing device are further caused to: receive the encryptedauthentication data generated by the contactless card based at least inpart on a private key for the contactless card stored in a memory of thecontactless card; transmit (i) the merchant ID of a merchant, (ii) thetransaction ID, and (iii) the encrypted authentication data to anauthentication server, the authentication server to verify the encryptedauthentication data by decrypting the encrypted authentication databased at least in part on the private key for the contactless cardstored in a memory of the authentication server; generate, based on theverification of the encrypted authentication data, a virtual accountnumber; transmit the merchant identifier, the transaction ID, thevirtual account number, an expiration date associated with the virtualaccount number, and a card verification value (CVV) associated with thevirtual account number to a merchant server associated with themerchant; and process, by the merchant server, the transaction using thetransaction ID, the virtual account number, the expiration date, and theCVV.
 10. The system of claim 1, wherein the in-vehicle device, thecomputing device, and the contactless card are all used or operated in avehicle. 11-20. (canceled)
 21. The system of claim 1, wherein thecontactless card further comprising: a memory storing one or moreinstructions; at least one communication interface; and one or moreprocessors, coupled with the memory, operable to execute the one or moreinstructions, that when executed, cause the one or more processors to:determine whether the at least one communication interface is in NFCcommunication with the NFC reader of the computing device in a firstinstance or in a second instance, the first instance being associatedwith the first tap and the second instance being associated with thesecond tap; and in response to the first tap, generate and transmitencrypted authentication data to the computing device and in response tothe second tap, generate and transmit a merchant identifier (ID) and atransaction (ID) to one or more external servers, and wherein thein-vehicle device communicates with an external device reader fordeducting a payment from the account.
 22. A computer-implemented methodcomprising: receiving one or more images of a unique identifierassociated with the in-vehicle device in response to the camera beingwithin a predefined distance from the in-vehicle device; receiving oneor more images of information for accessing an account associated withthe in-vehicle device in response to the camera being within thepredefined distance from the in-vehicle device, the informationincluding at least a uniform resource locator (URL) corresponding to theaccount; detecting a first tap of a contactless card belonging to a userand, in response to the first tap, authenticating the user, wherein theauthentication comprises: (i) detecting the contactless card via the NFCreader, the contactless card being tapped to the computing device by theuser, (ii) receiving encrypted data from the contactless card via NFC,the encrypted data including at least a customer identifier, thecustomer identifier being associated with the user (iii) performing userauthentication by: sending the encrypted data including the customeridentifier to one or more remote computing devices, wherein the one ormore remote computing devices performs at least decryption of the datausing a key, and receiving an indication or confirmation from the remotecomputing devices that the customer identifier matches the user, and(iv) determining that user authentication is successful based on thecustomer identifier matching the user; accessing, automatically inresponse to successful authentication of the user, the accountassociated with the in-vehicle device based on the URL and the uniqueidentifier of the in-vehicle device without requiring the user to enterlogin information; and detecting a second tap of the contactless card,and in response to the second tap, loading or reloading the accountassociated with the in-vehicle device with funds of a predeterminedvalue or amount, wherein the funds are linked to a banking accountcorresponding to the contactless card.
 23. The method of claim 22,wherein the in-vehicle device is a toll transponder, a device fordrive-thru payment service, a garage access badge, or a parking pass.24. The method of claim 22, wherein the unique identifier associatedwith the in-vehicle device is (i) a transponder identification number,(i) an account number corresponding to the drive-thru payment service,(iii) a badge number corresponding to the garage access badge, and/or(iv) pass number corresponding to the parking pass.
 25. The method ofclaim 22, wherein the account is provided via a payment applicationand/or a website.
 26. At least one non-transitory computer-readablestorage medium storing computer-readable program code executable by atleast one processor to: receive one or more images of a uniqueidentifier associated with the in-vehicle device in response to thecamera being within a predefined distance from the in-vehicle device;receive one or more images of information for accessing an accountassociated with the in-vehicle device in response to the camera beingwithin the predefined distance from the in-vehicle device, theinformation including at least a uniform resource locator (URL)corresponding to the account; detect a first tap of a contactless cardbelonging to a user and, in response to the first tap, authenticate theuser, wherein the authentication comprises: (i) detecting thecontactless card via the NFC reader, the contactless card being tappedto the computing device by the user, (ii) receiving encrypted data fromthe contactless card via NFC, the encrypted data including at least acustomer identifier, the customer identifier being associated with theuser (iii) performing user authentication by: sending the encrypted dataincluding the customer identifier to one or more remote computingdevices, wherein the one or more remote computing devices performs atleast decryption of the data using a key, and receiving an indication orconfirmation from the remote computing devices that the customeridentifier matches the user, and (iv) determining that userauthentication is successful based on the customer identifier matchingthe user; access, automatically in response to successful authenticationof the user, the account associated with the in-vehicle device based onthe URL and the unique identifier of the in-vehicle device withoutrequiring the user to enter login information; and detect a second tapof the contactless card, and in response to the second tap, load orreload the account associated with the in-vehicle device with funds of apredetermined value or amount, wherein the funds are linked to a bankingaccount corresponding to the contactless card.
 27. The at least onenon-transitory computer-readable storage medium of claim 26, wherein thein-vehicle device is a toll transponder, a device for drive-thru paymentservice, a garage access badge, or a parking pass.
 28. The at least onenon-transitory computer-readable storage medium of claim 26, wherein theunique identifier associated with the in-vehicle device is (i) atransponder identification number, (i) an account number correspondingto the drive-thru payment service, (iii) a badge number corresponding tothe garage access badge, and/or (iv) pass number corresponding to theparking pass.
 29. The at least one non-transitory computer-readablestorage medium of claim 26, wherein the account is provided via apayment application and/or a website.